fix: expose the fluent API fn for approx_distinct instead of the module #11644
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #11643
Which issue does this PR close?
Closes #11643 .
Rationale for this change
expr_fn
module should aggregate and expose the fluent APIs, not the modules which are exposed separately.What changes are included in this PR?
Update the re-export in
expr_fn
to expose the fluent API.Are these changes tested?
No additional tests.
Are there any user-facing changes?
Anyone that currently references
functions_aggregate::expr_fn::approx_distinct::aprox_distinct
will need to change that reference.